Dynamic media overlay with smart widget

ABSTRACT

Systems and methods are provided for receiving a background image for a media overlay to be applied to a message comprising an image or video, and at least one smart widget selection, and storing the media overlay comprising the background image and the at least one smart widget selection. The systems and methods further provide for receiving a request for the media overlay to be applied to a message comprising an image or video, analyzing context data associated with a computing device to determine that the media overlay is relevant to at least one aspect of the context data, determining data associated with the at least one smart widget based on the context data, and transmitting to the computing device, the media overlay and data associated with the at least one smart widget.

CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.15/829,588, filed on Dec. 1, 2017, which is incorporated herein byreference in its entirety.

BACKGROUND

A messaging system may receive millions of messages from users desiringto share media content such as audio, images, and video between userdevices (e.g., mobile devices, personal computers, etc.). The mediacontent of these messages may be associated with a common geolocation, acommon time period, a common event, and so forth.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present disclosure and should not be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating a networked system, according tosome example embodiments.

FIG. 2 illustrates example media overlays, according to some exampleembodiments.

FIG. 3 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a network,according to some example embodiments.

FIG. 4 is block diagram illustrating further details regarding amessaging system, according to some example embodiments.

FIG. 5 is a schematic diagram illustrating data which may be stored inthe database of the messaging server system, according to some exampleembodiments.

FIG. 6 is a schematic diagram illustrating a structure of a message,according to some embodiments, generated by a messaging clientapplication for communication.

FIG. 7 is a flow chart illustrating aspects of a method, according tosome example embodiments.

FIGS. 8-9 illustrate an example graphical user interface, according tosome example embodiments.

FIG. 10 illustrates example attributes for a smart widget, according tosome example embodiments.

FIG. 11 is a flow chart illustrating aspects of a method, according tosome example embodiments.

FIG. 12 is a block diagram illustrating an example of a softwarearchitecture that may be installed on a machine, according to someexample embodiments.

FIG. 13 illustrates a diagrammatic representation of a machine, in theform of a computer system, within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, according to an example embodiment.

DETAILED DESCRIPTION

Systems and methods described herein relate to dynamic media overlayswith one or more smart widgets that allow for dynamic content to bedisplayed in a media overlay for a message, based on context dataassociated with a computing device and/or a video or image. A smartwidget is a display element associated with dynamic content. Forexample, a creator of a media overlay may be an artist or designerassociated with a messaging network, a company, a service, or otherentity, or the creator may be an individual user not associated with anyparticular entity. The creator may wish to create a media overlay to bemade available to users that can display a location of the computingdevice associated with a user, information about audio playing on thecomputing device, event information associated with the location, userinformation, time or weather information, and so forth. For example, thecreator may want to create a “Cinco de Mayo” media overlay for theupcoming holiday on May 5th. Instead of creating a separate mediaoverlay for each location, or each potential event, weather, or whatnot, example embodiments allow the creator to add a smart widget to hismedia overlay image that will later fill in with a user's location orother information when the media overlay is displayed. This provides ascalable way of adding a location or other element to any media overlay,which significantly increases the media overlay's relevance and providesa more efficient system for providing media overlays.

A user may be creating a message comprising a photograph or video andtext. The user may be located in Venice and it may be May 5th. The usermay then be able to access the “Cinco de Mayo” media overlay to augmenthis message comprising the photograph or video. The media overlay wouldbe rendered on the user's device to display “Cinco de Mayo Venice” asshown in the example 202 in FIG. 2 . If the user was instead located inManhattan, the example 204 would be displayed on the user's device.

Example embodiments address a number of technical challenges and providea number of advantages. For example, typically a creator of a mediaoverlay would need to manually create a separate media overlay for eachlocation where the creator wanted the media overlay to be available.Using the “Cinco de Mayo” media overlay example above, the creator wouldhave to manually create a separate design for each city (e.g., SanFrancisco, Los Angeles, Albuquerque, Miami, etc.). This is not scalableto a single state or region, let alone an entire country or worldwide.This is especially true for current events or trends where a creatorwould want to create and release a media overlay quickly. Accordingly,example embodiments provide for a scalable solution that allows for afaster creation and release process. Instead of manually creatingseparate media overlays, a media overlay platform is provided thatallows a creator to set up media overlays that can dynamically displayairports, train stations, parks, and other location based data, as oneexample of dynamic data.

FIG. 1 is a block diagram illustrating a networked system 100, accordingto some example embodiments. The system 100 may include one or moreclient devices such as client device 110. The client device 110 maycomprise, but is not limited to, a mobile phone, desktop computer,laptop, portable digital assistant (PDA), smart phone, tablet,Ultrabook, netbook, laptop, multi-processor system, microprocessor-basedor programmable consumer electronic, game console, set-top box, computerin a vehicle, or any other communication device that a user may utilizeto access the networked system 100. In some embodiments, the clientdevice 110 may comprise a display module (not shown) to displayinformation (e.g., in the form of user interfaces). In furtherembodiments, the client device 110 may comprise one or more of touchscreens, accelerometers, gyroscopes, cameras, microphones, globalpositioning system (GPS) devices, and so forth. The client device 110may be a device of a user that is used to create or generate messagescomprising images (e.g., photographs), video, and/or text. The clientdevice 110 may be a device of a user that is used to create and editmedia overlays.

One or more users 106 may be a person, a machine, or other means ofinteracting with the client device 110. In example embodiments, the user106 may not be part of the system 100, but may interact with the system100 via the client device 110 or other means. For instance, the user 106may provide input (e.g., touch screen input or alphanumeric input) tothe client device 110, and the input may be communicated to otherentities in the system 100 (e.g., third party servers 130, server system102, etc.) via a network 104. In this instance, the other entities inthe system 100, in response to receiving the input from the user 106,may communicate information to the client device 110 via the network 104to be presented to the user 106. In this way, the user 106 may interactwith the various entities in the system 100 using the client device 110.

The system 100 may further include a network 104. One or more portionsof network 104 may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), a portion of the Internet, a portion ofthe public switched telephone network (PSTN), a cellular telephonenetwork, a wireless network, a WiFi network, a WiMax network, anothertype of network, or a combination of two or more such networks.

The client device 110 may access the various data and applicationsprovided by other entities in the system 100 via web client 112 (e.g., abrowser, such as the Internet Explorer® browser developed by Microsoft®Corporation of Redmond, Wash. State) or one or more client applications114. The client device 110 may include one or more client applications114 (also referred to as “apps”) such as, but not limited to, a webbrowser, messaging application, electronic mail (email) application, ane-commerce site application, a mapping or location application, mediaoverlay application, and the like.

In some embodiments, one or more client applications 114 may be includedin a given one of the client devices 110 and configured to locallyprovide the user interface and at least some of the functionalities,with the client application 114 configured to communicate with otherentities in the system 100 (e.g., third party servers 130, server system102, etc.), on an as needed basis, for data and/or processingcapabilities not locally available (e.g., to process user queries, toauthenticate a user 106, to verify a method of payment, etc.).Conversely, one or more applications 114 may not be included in theclient device 110, and then the client device 110 may use its webbrowser to access the one or more applications hosted on other entitiesin the system 100 (e.g., third party servers 130, server system 102,etc.).

A server system 102 may provide server-side functionality via thenetwork 104 (e.g., the Internet or wide area network (WAN)) to one ormore third party servers 130 and/or one or more client devices 110. Theserver system 102 may include an application program interface (API)server 120, a web server 122, and a media overlay platform server 124,which may be communicatively coupled with one or more databases 126.

The one or more databases 126 may be storage devices that store mediaoverlays, smart widgets, messaging data, user data, computing devicecontext data, media content data (e.g., data associate with video andimages), and other data. The one or more databases 126 may further storeinformation related to third party servers 130, third party applications132, client devices 110, client applications 114, users 106, and soforth. The one or more databases 126 may include cloud-based storage.

The server system 102 may be a cloud computing environment, according tosome example embodiments. The server system 102, and any serversassociated with the server system 102, may be associated with acloud-based application, in one example embodiment.

The media overlay platform server 124 may provide back-end support forthird-party applications 132 and client applications 114, which mayinclude cloud-based applications. In one embodiment, the media overlayplatform server 124 may receive requests from third party servers orclient devices for one or more media overlays, process the requests,provide one or more media overlays, and so forth. FIG. 2 show examplesmedia overlays 202 and 204 that may be created and then stored by themedia overlay platform server 124 and which may be accessed and analyzedby the media overlay platform server 124 for delivery to a computingdevice.

The system 100 may further include one or more third party servers 130.The one or more third party servers 130 may include one or more thirdparty application(s) 132. The one or more third party application(s)132, executing on third party server(s) 130, may interact with theserver system 102 via API server 120 via a programmatic interfaceprovided by the API server 120. For example, one or more the third partyapplications 132 may request and utilize information from the serversystem 102 via the API server 120 to support one or more features orfunctions on a website hosted by the third party or an applicationhosted by the third party. The third party website or application 132,for example, may provide functionality that is supported by relevantfunctionality and data in the server system 102.

FIG. 3 is a block diagram illustrating a networked system 300 (e.g., amessaging system) for exchanging data (e.g., messages and associatedcontent) over a network. The networked system 300 includes multipleclient devices 110, each of which hosts a number of client applications114. Each client application 114 is communicatively coupled to otherinstances of the client application 114 and a server system 308 via anetwork 104.

The client device 110, client application 114, and network 104, aredescribed above with respect to FIG. 1 . The client device 110 may be adevice of a user that is used to create media content items such asvideo, images (e.g., photographs), and audio, and send and receivemessages containing such media content items to and from other users.

In one example, a client application 114 may be a messaging applicationthat allows a user to take a photograph or video, add a caption, orotherwise edit the photograph or video, and then send the photograph orvideo to another user. In one example, the message may be ephemeral andbe removed from a receiving user device after viewing or after apredetermined amount of time (e.g., 10 seconds, 24 hours, etc.). Anephemeral message refers to a message that is accessible for atime-limited duration. An ephemeral message may be a text, an image, avideo, and other such content that may be stitched together inaccordance with embodiments described herein. The access time for theephemeral message may be set by the message sender. Alternatively, theaccess time may be a default setting or a setting specified by therecipient. Regardless of the setting technique, the message istransitory.

The messaging application may further allow a user to create a galleryor message collection. A gallery may be a collection of photos andvideos which may be viewed by other users “following” the user's gallery(e.g., subscribed to view and receive updates in the user's gallery). Inone example, the gallery may also be ephemeral (e.g., lasting 24 hours,lasting for a duration of an event (e.g., during a music concert,sporting event, etc.), or other predetermined time).

An ephemeral message may be associated with a message durationparameter, the value of which determines an amount of time that theephemeral message will be displayed to a receiving user of the ephemeralmessage by the client application 114. The ephemeral message may befurther associated with a message receiver identifier and a messagetimer. The message timer may be responsible for determining the amountof time the ephemeral message is shown to a particular receiving useridentified by the message receiver identifier. For example, theephemeral message may only be shown to the relevant receiving user for atime period determined by the value of the message duration parameter.

In another example, the messaging application may allow a user to storephotographs and videos and create a gallery that is not ephemeral andthat can be sent to other users. For example, a user may assemblephotographs and videos from a recent vacation to share with friends andfamily.

A server system 308 may provide server-side functionality via thenetwork 104 (e.g., the Internet or wide area network (WAN)) to one ormore client device 110. The server system 308 may include an applicationprogramming interface (API) server 310, an application server 312, amessaging application server 314, a media content processing system 316,and a social network system 322, which may each be communicativelycoupled with each other and with one or more data storage(s), such asdatabase(s) 320. The server system 308 may also comprise the serversystem 102 of FIG. 1 or at least the media overlay platform server 124of FIG. 1 .

The server system 308 may be a cloud computing environment, according tosome example embodiments. The server system 308, and any serversassociated with the server system 308, may be associated with acloud-based application, in one example embodiment. The one or moredatabase(s) 720 may be storage devices that store information such asuntreated media content, original media content from users (e.g.,high-quality media content), processed media content (e.g., mediacontent that is formatted for sharing with client devices 110 andviewing on client devices 110), context data related to a media contentitem, context data related to a user device (e.g., computing or clientdevice 110), media overlays, media overlay smart widgets or smartelements, user information, user device information, and so forth. Theone or more database(s) 320 may include cloud-based storage external tothe server system 308 (e.g., hosted by one or more third party entitiesexternal to the server system 308). While the storage devices are shownas database(s) 320, it is understood that the system 100 may access andstore data in storage devices such as databases 320, blob storages, andother type of storage methods.

Accordingly, each client application 114 is able to communicate andexchange data with other client applications 114 and with the serversystem 308 via the network 104. The data exchanged between clientapplications 114, and between a client application 114 and the serversystem 308, includes functions (e.g., commands to invoke functions) aswell as payload data (e.g., text, audio, video or other multimediadata).

The server system 308 provides server-side functionality via the network104 to a particular client application 114. While certain functions ofthe system 300 are described herein as being performed by either aclient application 114 or by the server system 308, it will beappreciated that the location of certain functionality either within theclient application 114 or the server system 308 is a design choice. Forexample, it may be technically preferable to initially deploy certaintechnology and functionality within the server system 308, but to latermigrate this technology and functionality to the client application 114where a client device 110 has a sufficient processing capacity.

The server system 308 supports various services and operations that areprovided to the client application 114. Such operations includetransmitting data to, receiving data from, and processing data generatedby the client application 114. This data may include message content,client device information, geolocation information, media annotation andoverlays, message content persistence conditions, social networkinformation, live event information, and date and time stamps, asexamples. Data exchanges within the networked system 300 are invoked andcontrolled through functions available via user interfaces (UIs) of theclient application 114.

In the server system 308, an application program interface (API) server310 is coupled to, and provides a programmatic interface to, anapplication server 312. The application server 312 is communicativelycoupled to a database server 318, which facilitates access to one ormore database(s) 320 in which is stored data associated with messagesprocessed by the application server 312.

The API server 310 receives and transmits message data (e.g., commandsand message payloads) between the client device 110 and the applicationserver 312. Specifically, the API server 310 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the client application 114 in order to invoke functionality of theapplication server 312. The API server 310 exposes various functionssupported by the application server 312, including account registration;login functionality; the sending of messages, via the application server312, from a particular client application 114 to another clientapplication 114; the sending of media files (e.g., images or video) froma client application 114 to the messaging application server 314, andfor possible access by another client application 114; the setting of acollection of media data (e.g., a gallery, story, message collection, ormedia collection); the retrieval of such collections; the retrieval of alist of friends of a user of a client device 110; the retrieval ofmessages and content; the adding and deletion of friends to a socialgraph; the location of friends within a social graph; opening anapplication event (e.g., relating to the client application 114); and soforth.

The application server 312 hosts a number of applications andsubsystems, including a messaging application server 314, a mediacontent processing system 316, and a social network system 322. Themessaging application server 314 implements a number of messageprocessing technologies and functions, particularly related to theaggregation and other processing of content (e.g., textual andmultimedia content) included in messages received from multipleinstances of the messaging client application 114. The text and mediacontent from multiple sources may be aggregated into collections ofcontent (e.g., called stories or galleries). These collections are thenmade available, by the messaging application server 314, to the clientapplication 114. Other processor- and memory-intensive processing ofdata may also be performed server-side by the messaging applicationserver 314, in view of the hardware requirements for such processing.

The application server 312 also includes a media content processingsystem 316 that is dedicated to performing various media contentprocessing operations, typically with respect to images or videoreceived within the payload of a message at the messaging applicationserver 314. The media content processing system 316 may access one ormore data storages (e.g., database(s) 320) to retrieve stored data touse in processing media content and to store results of processed mediacontent.

The social network system 322 supports various social networkingfunctions and services, and makes these functions and services availableto the messaging application server 314. To this end, the social networksystem 322 maintains and accesses an entity graph 504 (depicted in FIG.5 ) within the database 320. Examples of functions and servicessupported by the social network system 322 include the identification ofother users of the networked system 300 with which a particular user hasrelationships or is “following,” and also the identification of otherentities and interests of a particular user.

The messaging application server 314 may be responsible for generationand delivery of messages between users of client devices 110. Themessaging application server 314 may utilize any one of a number ofmessage delivery networks and platforms to deliver messages to users.For example, the messaging application server 314 may deliver messagesusing electronic mail (e-mail), instant message (IM), Short MessageService (SMS), text, facsimile, or voice (e.g., Voice over IP (VoIP))messages via wired networks (e.g., the Internet), plain old telephoneservice (POTS), or wireless networks (e.g., mobile, cellular, WiFi, LongTerm Evolution (LTE), Bluetooth).

FIG. 4 is block diagram 400 illustrating further details regarding thesystem 300, according to example embodiments. Specifically, the diagram400 is shown to comprise the messaging client application 114 and theapplication server 312, which in turn embody a number of subsystems,namely an ephemeral timer system 402, a collection management system404, and an annotation system 406.

The ephemeral timer system 402 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 114 and the messaging application server 314. To this end,the ephemeral timer system 402 incorporates a number of timers that,based on duration and display parameters associated with a message, orcollection of messages (e.g., otherwise referred to herein as mediacollections, galleries, message collections, stories, and the like),selectively display and enable access to messages and associated contentvia the messaging client application 114.

The collection management system 404 is responsible for managingcollections of media (e.g., collections of text, image, video, and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text, and audio) may be organized into an“event gallery” or an “event story.” Such a collection may be madeavailable for a specified time period, such as the duration of an eventto which the content relates. For example, content relating to a musicconcert may be made available as a “Story” for the duration of thatmusic concert. The collection management system 404 may also beresponsible for publishing an icon that provides notification of theexistence of a particular collection to the user interface of themessaging client application 114.

The collection management system 404 furthermore includes a curationinterface 408 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface408 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 404employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation (e.g., money, non-money credits or pointsassociated with the communication system or a third party reward system,travel miles, access to artwork or specialized lenses, etc.) may be paidto a user for inclusion of user-generated content into a collection. Insuch cases, the curation interface 408 operates to automatically makepayments to such users for the use of their content.

The annotation system 406 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 406 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the networked system 300. In one example, the annotationsystem 406 operatively supplies a media overlay (e.g., a filter or mediaaugmentation) to the messaging client application 114 based on ageolocation of the client device 110. In another example, the annotationsystem 406 operatively supplies a media overlay to the messaging clientapplication 114 based on other information, such as social networkinformation of the user of the client device 110. A media overlay mayinclude audio and visual content and visual effects. Examples of audioand visual content include pictures, texts, logos, animations, and soundeffects. An example of a visual effect includes color overlaying. Theaudio and visual content or the visual effects can be applied to a mediacontent item (e.g., a photo) at the client device 110. For example, themedia overlay includes text that can be overlaid on top of a photographtaken by the client device 110. In another example, the media overlayincludes an identification of a location overlay (e.g., Venice beach), aname of a live event, or a name of a merchant overlay (e.g., BeachCoffee House). In another example, the annotation system 406 uses thegeolocation of the client device 110 to identify a media overlay thatincludes the name of a merchant at the geolocation of the client device110. The media overlay may include other indicia associated with themerchant. The media overlays may be stored in the database 320 andaccessed through the database server 318.

In one example embodiment, the annotation system 406 provides auser-based publication platform that enables users to select ageolocation on a map and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay is to be offered to other users. The annotationsystem 406 generates a media overlay that includes the uploaded contentand associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system 406 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 406 associates the mediaoverlay of a highest bidding merchant with a corresponding geolocationfor a predefined amount of time.

In another example embodiment, the annotation system 406 provides one ormore smart widgets, comprising one or more dynamic elements, that may beincluded with a media overlay to allow for a dynamic media overlay to bepresented to a user based on various context data associated with theuser or user device, such as location, event, and so forth.Functionality related to smart widgets are described in further detailbelow.

FIG. 5 is a schematic diagram 500 illustrating data which may be storedin the database(s) 320 of the server system 308, according to certainexample embodiments. While the content of the database 320 is shown tocomprise a number of tables, it will be appreciated that the data couldbe stored in other types of data structures (e.g., as an object-orienteddatabase).

The database 320 includes message data stored within a message table514. The entity table 502 stores entity data, including an entity graph504. Entities for which records are maintained within the entity table502 may include individuals, corporate entities, organizations, objects,places, events, and the like. Regardless of type, any entity regardingwhich the server system 308 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 504 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization), interest-based, or activity-based, merely for example.

The database 320 also stores annotation data, in the example form ofmedia overlays or filters, in an annotation table 512. Annotation datamay also be referred to herein as “creative tools.” Media overlays orfilters, for which data is stored within the annotation table 512, areassociated with and applied to videos (for which data is stored in avideo table 510) and/or images (for which data is stored in an imagetable 508). Filters, in one example, are overlays that are displayed asoverlaid on an image or video during presentation to a recipient user.Filters may be of various types, including user-selected filters from agallery of filters presented to a sending user by the messaging clientapplication 114 when the sending user is composing a message. Othertypes of filters include geolocation filters (also known as geo-filters)which may be presented to a sending user based on geographic location.For example, geolocation filters specific to a neighborhood or speciallocation may be presented within a user interface by the messagingclient application 114, based on geolocation information determined by aGPS unit of the client device 110. Another type of filter is a datafilter, which may be selectively presented to a sending user by themessaging client application 114, based on other inputs or informationgathered by the client device 110 during the message creation process.Example of data filters include current temperature at a specificlocation, a current speed at which a sending user is traveling, batterylife for a client device 110, or the current time.

Other annotation data that may be stored within the image table 508 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 510 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 514. Similarly, the image table 508 storesimage data associated with messages for which message data is stored inthe entity table 502. The entity table 502 may associate variousannotations from the annotation table 512 with various images and videosstored in the image table 508 and the video table 510.

A story table 506 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story, gallery, or media collection). The creationof a particular collection may be initiated by a particular user (e.g.,each user for which a record is maintained in the entity table 502). Auser may create a “personal story” in the form of a collection ofcontent that has been created and sent/broadcast by that user. To thisend, the user interface of the messaging client application 114 mayinclude an icon that is user-selectable to enable a sending user to addspecific content to his or her personal story.

A media or message collection may also constitute a “live story,” whichis a collection of content from multiple users that is created manually,automatically, or using a combination of manual and automatictechniques. For example, a “live story” may constitute a curated streamof user-submitted content from various locations and events. Users,whose client devices 110 have location services enabled and are at acommon location or event at a particular time, may, for example, bepresented with an option, via a user interface of the messaging clientapplication 114, to contribute content to a particular live story. Thelive story may be identified to the user by the messaging clientapplication 114, based on his or her location. The end result is a “livestory” told from a community perspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 110 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 6 is a schematic diagram illustrating a structure of a message 600,according to some embodiments, generated by a client application 114 forcommunication to a further client application 114 or the messagingapplication server 314. The content of a particular message 600 is usedto populate the message table 514 stored within the database 320,accessible by the messaging application server 314. Similarly, thecontent of a message 600 is stored in memory as “in-transit”or“in-flight” data of the client device 110 or the application server 312.The message 600 is shown to include the following components:

-   -   A message identifier 602: a unique identifier that identifies        the message 600.    -   A message text payload 604: text, to be generated by a user via        a user interface of the client device 110 and that is included        in the message 600.    -   A message image payload 606: image data, captured by a camera        component of a client device 110 or retrieved from memory of a        client device 110, and that is included in the message 600.    -   A message video payload 608: video data, captured by a camera        component or retrieved from a memory component of the client        device 110 and that is included in the message 600.    -   A message audio payload 610: audio data, captured by a        microphone or retrieved from the memory component of the client        device 110, and that is included in the message 600.    -   A message annotations 612: annotation data (e.g., media overlays        such as filters, stickers, or other enhancements) that        represents annotations to be applied to message image payload        606, message video payload 608, or message audio payload 610 of        the message 600.    -   A message duration parameter 614: parameter value indicating, in        seconds, the amount of time for which content of the message 600        (e.g., the message image payload 606, message video payload 608,        message audio payload 610) is to be presented or made accessible        to a user via the messaging client application 114.    -   A message geolocation parameter 616: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message 600. Multiple message geolocation        parameter 616 values may be included in the payload, with each        of these parameter values being associated with respect to        content items included in the content (e.g., a specific image        within the message image payload 606 or a specific video in the        message video payload 608).    -   A message story identifier 618: identifier values identifying        one or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 606 of the        message 600 is associated. For example, multiple images within        the message image payload 606 may each be associated with        multiple content collections using identifier values.    -   A message tag 620: each message 600 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 606        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 620 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 622: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 110 on        which the message 600 was generated and from which the message        600 was sent.    -   A message receiver identifier 624: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 110 to        which the message 600 is addressed.

The contents (e.g., values) of the various components of message 600 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 606 maybe a pointer to (or address of) a location within an image table 508.Similarly, values within the message video payload 608 may point to datastored within a video table 510, values stored within the messageannotations 612 may point to data stored in an annotation table 512,values stored within the message story identifier 618 may point to datastored in a story table 506, and values stored within the message senderidentifier 622 and the message receiver identifier 624 may point to userrecords stored within an entity table 502.

FIG. 7 is a flow chart illustrating aspects of a method, according tosome example embodiments. For illustrative purposes, method 700 isdescribed with respect to the networked system 100 of FIG. 1 . It is tobe understood that method 700 may be practiced with other systemconfigurations in other embodiments.

In operation 702, a computing system (e.g., server system 102 or mediaoverlay platform server 124) receives a background image for a mediaoverlay to be applied to a message comprising an image or video. Forexample, a graphical user interface (GUI) may be provided to a creatorof a media overlay (e.g., an artist or designer associated with amessaging network, a company, a service, or other entity, or the creatormay be an individual user not associated with any particular entity) viaa computing device (e.g., client device 110) to create the mediaoverlay. FIG. 8 shows an example GUI 800 for creating a media overlay.In the example of FIG. 8 , the creator has uploaded a background image802 (e.g., a .png file) and has selected the “Smart Location” smartwidget 806 from a selection of a plurality of smart widgets 804. Thelist of smart widgets in the example GUI 800 is an example of possiblesmart widgets. In other embodiments, there may be more of a selection ofsmart widgets, less of a selection of smart widgets, or a differentselection of smart widgets than what is shown in FIG. 8 .

The creator may select the smart location by interacting with the GUI(e.g., touching a display of the computing device, using one or morebuttons on the computing device, using a mouse or other device tointeract with the display, etc.). In response to the selection of thesmart widget, a box or other visual element may appear on the backgroundfor the media overlay. This box may be moved to the location desired onthe media overlay and resized to the size at which the creator wishesthe smart widget to be displayed. The box may also be rotated.

The GUI further provides tools 808 for providing attributes to beassociated with the smart widget. For example, the creator of the mediaoverlay may select a font type, capitalization (e.g., all caps, CamelCase, first word capitalized, all lower case, etc.), shadowing (color,radius, x/y offsets, with some presets, etc.), alignment of text (e.g.,left, center, right), color, and a preview of how text for the smartwidget may appear. FIG. 10 shows example interface elements 1002-1012for each of these attribute options. These attributes are just exampleattributes. More, less, or different attributes may be provided in theGUI. Other examples of attributes may be underlining, italics, fontsize, transparency, bold, and so forth.

The GUI may further provide an option to choose the granularity for thesmart widget, as shown in FIG. 9 . In the GUI 900 of FIG. 9 , agranularity element 902 is displayed for the creator to input the levelof granularity for the location. For example, the creator may choosecity, state, neighborhood, city and state initials, zip code, country,county, school, college, airport, train station, venue, or otherlocation. For example, a city selection may display “Seattle,” a cityand state initials may display “Seattle, Wash.,” a state may display“New York,” a state initials may display “NY,” a zip code may display“94706,” neighborhood may display “Santa Monica,” a high school maydisplay “Los Angeles High School,” a college may display “CaliforniaState University,” an airport may display “LAX,” and so forth. The GUImay further provide an option to input default text for when locationinformation may be unavailable (e.g., the computing system cannot getGPS or other location data from a computing device). The GUI 800 or 900may further provide an option 810 to save the media overlay.

Returning to FIG. 7 , after the computing system receives the backgroundimage (e.g., uploaded .png file) for the media overlay, it receives atleast one smart widget selection to be associated with the media overlayin operation 704. For example, the computing system may receive aselection of a smart location widget or one or more other smart widgetsvia the GUI 800. The computing system may further receive attributes foreach selected smart widget. As explained above, an attribute may includea location of the widget on the media overlay, a font for textassociated with the smart widget, a color for text associated with thesmart widget, a bounding box for text associated with the smart widget,a maximum font size for text associated with the smart widget, a minimumfont size for text associated with the smart widget, an alignment fortext associated with the smart widget, a shadow for text associated withthe smart widget, a default spelling for text associated with the smartwidget, a transparency value for text associated with the smart widget,and so forth.

In operation 706, the computing system stores the media overlaycomprising the background image and the one or more smart widgetselections in one or more databases (e.g., database 126 or 320). Themedia overlay may be stored separate from the one or more smart widgets.For example, the media overlay may be stored as a .png image and the oneor more smart widgets may be stored separately and associated with oneor more elements (e.g., font type, alignment, etc.). The stored mediaoverlay may be provided to a computing device to be applied to a messagecomprising a video or an image.

In operation 708, the computing system receives, from a computing device(e.g., client device 110), a request for a media overlay to be appliedto a message comprising a video or image. The request may comprisecontext data (e.g., a location of the computing device, audio playing onthe computing device (e.g., song, speech, etc.), weather at the locationof computing device, time of day, day of the week, name of a userassociated with the computing device, etc.) associated with thecomputing device. For example, a user associated with the computingdevice may use the computing device to capture the video or image usinga camera of the computing device. The user may wish to augment the videoor image with text, a media overlay, a lens, or other creative tool. Thecomputing device may detect that the user is capturing an image or videoand send a request to the computing system to request media overlays toprovide to the user. The request may comprise context data associatedwith the computing device, such as GPS or other location information,user information, information associated with the image or video, a copyor portion of the image or video, weather data, time data, date data, orother information.

In operation 710, the computing system may analyze the request todetermine whether one or more media overlays are relevant to one or moreaspects (e.g., elements) of the context data. In one example, mediaoverlays may be associated with one or more triggers for which they arerelevant to be sent to a computing device. Example triggers may be ageolocation (e.g., city, state, venue, restaurant, location of interest,school, etc.), time of day (e.g., breakfast time, sunrise, commute time,3:30 pm, etc.), date (e.g., Wednesday, a holiday, the date of an event,etc.), audio detected by the computing device (e.g., background audio,audio associated with a video being captured, etc.), and so forth. Forexample, the media overlay in FIG. 2 may be triggered if the date is May5th. Another media overlay may be triggered if the computing device islocated in a particular venue (e.g., concert venue, theater, etc.).Another media overlay may be triggered based on a time of day, such asmorning, or sunset. And yet another media overlay may be triggered basedon a song being detected.

For example, the computing system may analyze the context data todetermine whether data in the context data triggers one or more mediaoverlays of a plurality of media overlays. In one example, the computingsystem may determine that the context data comprises geolocation data.The computing system compares the geolocation data of the context datato a geolocation trigger for one or more of the plurality of mediaoverlays to determine a match between the geolocation data of thecontext data and a geolocation trigger for one or more media overlays.

In another example, the computing system determines that the contextdata comprises geolocation data and determines that the geolocation datais associated with an event. For example, the computing system may usemap data (e.g., stored in one or more databases 320 or via third partysources) to determine that there is a concert venue associated with thegeolocation and use event scheduling data (e.g., stored in one or moredatabases 320 or via third party sources) for the concert venue todetermine that a particular concert is currently occurring at theconcert venue. The computing system compares the event (e.g., theparticular concert) to an event trigger (e.g., a trigger for thatparticular concert) for one or more media overlays to determine a matchbetween the event associated with the geolocation data of the contextdata and an event trigger for one or more media overlays.

In another example, the computing system determines that the contextdata comprises a date for an image or video to be included in a message.The computing system compares the date for the image or video to a datetrigger for one or more media overlays to determine a match between thedate for the image or video and a date trigger for one or more mediaoverlays.

In yet another example, the computing system determines that the contextdata includes a portion of an audio stream or an audio footprint. Thecomputing system may determine that the audio is for a particular songor speech, associated with a particular artist, or the like. Thecomputing system compares the song name, speech, artist name, or thelike, to an audio trigger for one or more media overlays to determine amatch between the audio in the context data and the audio trigger forone or more media overlays.

In this way, the computing system determines that one or more mediaoverlays is relevant to provide to the computing device. In anotherexample, the computing device may request one or more specific mediaoverlays.

In operation 712, for each relevant media overlay (or for eachspecifically requested media overlay), the computing system accesses themedia overlay and determines whether the media overlay comprises one ormore smart widgets. For example, the computing system may access themedia overlay in the one or more databases and also access informationassociated with the media overlay that indicates that one or more smartwidgets are associated with the media overlay.

In operation 714, the computing system determines data associated withthe one or more smart widgets. For example, the computing system may usethe context data received from the computing device, other data (e.g.,data associated with a user of the computing device, date or timeinformation, etc.), data derived from the context data (e.g., venue orplace of interest from geolocation information in the context data), andso forth, to determine the date for the one or more smart widgets. Usingthe example media overlay in FIG. 2 , the computing device may determinethat the computing device is located in Venice and thus, Venice is thedata that is associated with the location smart widget in this example(e.g., the data string “Venice”).

In operation 716, the computing system transmits the media overlay anddata associated with the at least one smart widget to the computingdevice. The data associated with the at least one smart widget may alsocomprise attributes associated with the smart widget. After receivingthe media overlay and data associated with the at least one smart widgetfor the media overlay, the computing device renders the content for theat least one media overlay. For example, the computing device wouldrender the text “Cinco de Mayo Venice” using data for the city name andin the font, color, and so forth indicated by the attributes for thesmart widget. The computing device would then apply the media overly“Cinco de Mayo Venice” to the user's video or image.

FIG. 11 is a flow chart illustrating aspects of a method, according tosome example embodiments, for rendering a media overlay. Forillustrative purposes, method 1100 is described with respect to thenetworked system 100 of FIG. 1 . It is to be understood that method 1100may be practiced with other system configurations in other embodiments.

In operation 1102, the computing device sends a request for one or moremedia overlays, as described above (e.g., a request for one or morespecific media overlays or for relevant media overlays) to the computingsystem. The computing device may generate the context data for therequest based on GPS or other location data detected by the computingdevice, data from the image or video (e.g., object recognition ofelements within the image or video, audio, etc.), speed detected by anaccelerometer or other means, altitude detected by the computing device,time of day or local time zone, day of the week, weather, temperature, aQuick Response (QR) Code or bar code, and so forth. The computing devicereceives the requested one or more media overlays in operation 1104,from the computing system.

In operation 1106, the computing device determines that the mediaoverlay comprises one or more smart widgets based on the data receivedwith the media overlay from the computing system. For example, the datamay specify the one or more smart widgets, or the fact that there areone or more smart widgets may be inferred by the amount and type of datareceived by the computing device.

In operation 1108, the computing device renders the content for thesmart widget and applies it to the media overlay. For example, thecomputing device would render the text “Cinco de Mayo Venice” using datafor the city name and in the font, color, and so forth indicated by theattributes for the smart widget. For example, the computing device maytake the text “Venice” and fit it into a bounding box based on theattributes, such as font type and alignment, and resize intelligently ifnecessary to fit it within the bounding box. The computing deviceapplies the color, shadow, and other attributes. The computing deviceapplies the rendered content on the media overlay to generate the mediaoverlay to display to the user.

The user may then select the media overlay to be applied to a messagecomprising an image or video. The computing device receives theselection and in 1110, applies the media overlay with the renderedcontent for the smart widget to the message (e.g., the media overlay isoverlaid on the image or video in the message), and displays the mediaoverlay with the rendered content for the smart widget on a display ofthe computing device, in operation 1112. For example, the computingdevice would then apply the media overly “Cinco de Mayo Venice” to theuser's video or image.

The user may wish to send the message to one or more other users. Thecomputing device may receive a request from the user to send themessage, and send the message comprising the media overlay and therendered content for the smart widget, in operation 1114. For example,the computing device may send the message via the computing system tothe one or more users. The computing system receives the messagecomprising the background image and the rendered content for the smartwidget (this could be separate or in one file), and then the computingsystem sends the message to the one or more users. The message with themedia overlay and rendered smart widget is then displayed on a computingdevice for the one or more users.

Example embodiments describe certain processes or actions performed by acomputing system and/or a computing device. It is understood that inother embodiments the computing system and/or computing device mayperform all or a different subset of the processes or actions described.

FIG. 12 is a block diagram 1200 illustrating software architecture 1202,which can be installed on any one or more of the devices describedabove. For example, in various embodiments, client devices 110 andserver systems 102, 120, 122, 124, 130, 308, 310, 312, 314, 316, 322 maybe implemented using some or all of the elements of softwarearchitecture 1202. FIG. 12 is merely a non-limiting example of asoftware architecture, and it will be appreciated that many otherarchitectures can be implemented to facilitate the functionalitydescribed herein. In various embodiments, the software architecture 1202is implemented by hardware such as machine 1300 of FIG. 13 that includesprocessors 1310, memory 1330, and input/output (V/O) components 1350. Inthis example, the software architecture 1202 can be conceptualized as astack of layers where each layer may provide a particular functionality.For example, the software architecture 1202 includes layers such as anoperating system 1204, libraries 1206, frameworks 1208, and applications1210. Operationally, the applications 1210 invoke API calls 1212 throughthe software stack and receive messages 1214 in response to the APIcalls 1212, consistent with some embodiments.

In various implementations, the operating system 1204 manages hardwareresources and provides common services. The operating system 1204includes, for example, a kernel 1220, services 1222, and drivers 1224.The kernel 1220 acts as an abstraction layer between the hardware andthe other software layers, consistent with some embodiments. Forexample, the kernel 1220 provides memory management, processormanagement (e.g., scheduling), component management, networking, andsecurity settings, among other functionality. The services 1222 canprovide other common services for the other software layers. The drivers1224 are responsible for controlling or interfacing with the underlyinghardware, according to some embodiments. For instance, the drivers 1224can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH®Low Energy drivers, flash memory drivers, serial communication drivers(e.g., Universal Serial Bus (USB) drivers), WI-FI® drivers, audiodrivers, power management drivers, and so forth.

In some embodiments, the libraries 1206 provide a low-level commoninfrastructure utilized by the applications 1210. The libraries 1206 caninclude system libraries 1230 (e.g., C standard library) that canprovide functions such as memory allocation functions, stringmanipulation functions, mathematic functions, and the like. In addition,the libraries 1206 can include API libraries 1232 such as medialibraries (e.g., libraries to support presentation and manipulation ofvarious media formats such as Moving Picture Experts Group-4 (MPEG4),Advanced Video Coding (H.264 or AVC), Moving Picture Experts GroupLayer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR)audio codec, Joint Photographic Experts Group (JPEG or JPG), or PortableNetwork Graphics (PNG)), graphics libraries (e.g., an OpenGL frameworkused to render in two dimensions (2D) and in three dimensions (3D)graphic content on a display), database libraries (e.g., SQLite toprovide various relational database functions), web libraries (e.g.,WebKit to provide web browsing functionality), and the like. Thelibraries 1206 can also include a wide variety of other libraries 1234to provide many other APIs to the applications 1210.

The frameworks 1208 provide a high-level common infrastructure that canbe utilized by the applications 1210, according to some embodiments. Forexample, the frameworks 1208 provide various graphic user interface(GUI) functions, high-level resource management, high-level locationservices, and so forth. The frameworks 1208 can provide a broad spectrumof other APIs that can be utilized by the applications 1210, some ofwhich may be specific to a particular operating system 1204 or platform.

In an example embodiment, the applications 1210 include a homeapplication 1250, a contacts application 1252, a browser application1254, a book reader application 1256, a location application 1258, amedia application 1260, a messaging application 1262, a game application1264, and a broad assortment of other applications such as a third partyapplications 1266. According to some embodiments, the applications 1210are programs that execute functions defined in the programs. Variousprogramming languages can be employed to create one or more of theapplications 1210, structured in a variety of manners, such asobject-oriented programming languages (e.g., Objective-C, Java, or C++)or procedural programming languages (e.g., C or assembly language). In aspecific example, the third party application 1266 (e.g., an applicationdeveloped using the ANDROID™ or IOS™ software development kit (SDK) byan entity other than the vendor of the particular platform) may bemobile software running on a mobile operating system such as IOS™,ANDROID™. WINDOWS® Phone, or another mobile operating system. In thisexample, the third party application 1266 can invoke the API calls 1212provided by the operating system 1204 to facilitate functionalitydescribed herein.

Some embodiments may particularly include a media overlay application1267. In certain embodiments, this may be a stand-alone application thatoperates to manage communications with a server system such as thirdparty servers 130 or server systems 102 or 708. In other embodiments,this functionality may be integrated with another application (e.g.,messaging application 1262). The media overlay application 1267 mayrequest and display various data related to messaging, media content,media collections, media overlays, and so forth, and may provide thecapability for a user 106 to input data related to the system via atouch interface, keyboard, or using a camera device of machine 1300,communication with a server system via I/O components 1350, and receiptand storage of object data in memory 1330. Presentation of informationand user inputs associated with the information may be managed by mediaoverlay application 1267 using different frameworks 1208, library 1206elements, or operating system 1204 elements operating on a machine 1200.

FIG. 13 is a block diagram illustrating components of a machine 1300,according to some embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 13 shows a diagrammatic representation of the machine1300 in the example form of a computer system, within which instructions1316 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1300 to perform any oneor more of the methodologies discussed herein can be executed. Inalternative embodiments, the machine 1300 operates as a standalonedevice or can be coupled (e.g., networked) to other machines. In anetworked deployment, the machine 1300 may operate in the capacity of aserver machine or system 102, 120, 122, 124, 130, 308, 310, 312, 314,316, 322, and the like, or a client device 110 in a server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine 1300 can comprise, but notbe limited to, a server computer, a client computer, a personal computer(PC), a tablet computer, a laptop computer, a netbook, a personaldigital assistant (PDA), an entertainment media system, a cellulartelephone, a smart phone, a mobile device, a wearable device (e.g., asmart watch), a smart home device (e.g., a smart appliance), other smartdevices, a web appliance, a network router, a network switch, a networkbridge, or any machine capable of executing the instructions 1316,sequentially or otherwise, that specify actions to be taken by themachine 1300. Further, while only a single machine 1300 is illustrated,the term “machine” shall also be taken to include a collection ofmachines 1300 that individually or jointly execute the instructions 1216to perform any one or more of the methodologies discussed herein.

In various embodiments, the machine 1300 comprises processors 1310,memory 1330, and 1/O components 1350, which can be configured tocommunicate with each other via a bus 1302. In an example embodiment,the processors 1310 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a radio-frequency integrated circuit (RFIC), another processor,or any suitable combination thereof) include, for example, a processor1312 and a processor 1314 that may execute the instructions 1316. Theterm “processor” is intended to include multi-core processors 1310 thatmay comprise two or more independent processors 1312, 1314 (alsoreferred to as “cores”) that can execute instructions 1316contemporaneously. Although FIG. 13 shows multiple processors 1310, themachine 1300 may include a single processor 1310 with a single core, asingle processor 1310 with multiple cores (e.g., a multi-core processor1310), multiple processors 1312, 1314 with a single core, multipleprocessors 1312, 1314 with multiples cores, or any combination thereof.

The memory 1330 comprises a main memory 1332, a static memory 1334, anda storage unit 1336 accessible to the processors 1310 via the bus 1302,according to some embodiments. The storage unit 1336 can include amachine-readable medium 1338 on which are stored the instructions 1316embodying any one or more of the methodologies or functions describedherein. The instructions 1316 can also reside, completely or at leastpartially, within the main memory 1332, within the static memory 1334,within at least one of the processors 1310 (e.g., within the processor'scache memory), or any suitable combination thereof, during executionthereof by the machine 1300. Accordingly, in various embodiments, themain memory 1332, the static memory 1334, and the processors 1310 areconsidered machine-readable media 1338.

As used herein, the term “memory” refers to a machine-readable medium1338 able to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 1338 is shown, in an example embodiment, to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storethe instructions 1316. The term “machine-readable medium” shall also betaken to include any medium, or combination of multiple media, that iscapable of storing instructions (e.g., instructions 1316) for executionby a machine (e.g., machine 1300), such that the instructions 1316, whenexecuted by one or more processors of the machine 1300 (e.g., processors1310), cause the machine 1300 to perform any one or more of themethodologies described herein. Accordingly, a “machine-readable medium”refers to a single storage apparatus or device, as well as “cloud-based”storage systems or storage networks that include multiple storageapparatus or devices. The term “machine-readable medium” shallaccordingly be taken to include, but not be limited to, one or more datarepositories in the form of a solid-state memory (e.g., flash memory),an optical medium, a magnetic medium, other non-volatile memory (e.g.,erasable programmable read-only memory (EPROM)), or any suitablecombination thereof. The term “machine-readable medium” specificallyexcludes non-statutory signals per se.

The I/O components 1350 include a wide variety of components to receiveinput, provide output, produce output, transmit information, exchangeinformation, capture measurements, and so on. In general, it will beappreciated that the I/O components 1350 can include many othercomponents that are not shown in FIG. 13 . The I/O components 1350 aregrouped according to functionality merely for simplifying the followingdiscussion, and the grouping is in no way limiting. In various exampleembodiments, the I/O components 1350 include output components 1352 andinput components 1354. The output components 1352 include visualcomponents (e.g., a display such as a plasma display panel (PDP), alight emitting diode (LED) display, a liquid crystal display (LCD), aprojector, or a cathode ray tube (CRT)), acoustic components (e.g.,speakers), haptic components (e.g., a vibratory motor), other signalgenerators, and so forth. The input components 1354 include alphanumericinput components (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point-based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstruments), tactile input components (e.g., a physical button, a touchscreen that provides location and force of touches or touch gestures, orother tactile input components), audio input components (e.g., amicrophone), and the like.

In some further example embodiments, the I/O components 1350 includebiometric components 1356, motion components 1358, environmentalcomponents 1360, or position components 1362, among a wide array ofother components. For example, the biometric components 1356 includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1358 includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 1360 include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensor components(e.g., machine olfaction detection sensors, gas detection sensors todetect concentrations of hazardous gases for safety or to measurepollutants in the atmosphere), or other components that may provideindications, measurements, or signals corresponding to a surroundingphysical environment. The position components 1362 include locationsensor components (e.g., a Global Positioning System (GPS) receivercomponent), altitude sensor components (e.g., altimeters or barometersthat detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication can be implemented using a wide variety of technologies.The I/O components 1350 may include communication components 1364operable to couple the machine 1300 to a network 1380 or devices 1370via a coupling 1382 and a coupling 1372, respectively. For example, thecommunication components 1364 include a network interface component oranother suitable device to interface with the network 1380. In furtherexamples, communication components 1364 include wired communicationcomponents, wireless communication components, cellular communicationcomponents, near field communication (NFC) components, BLUETOOTH®components (e.g., BLUETOOTH® Low Energy), WI-FI® components, and othercommunication components to provide communication via other modalities.The devices 1370 may be another machine 1300 or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, in some embodiments, the communication components 1364 detectidentifiers or include components operable to detect identifiers. Forexample, the communication components 1364 include radio frequencyidentification (RFID) tag reader components, NFC smart tag detectioncomponents, optical reader components (e.g., an optical sensor to detecta one-dimensional bar codes such as a Universal Product Code (UPC) barcode, multi-dimensional bar codes such as a Quick Response (QR) code,Aztec Code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code,Uniform Commercial Code Reduced Space Symbology (UCC RSS)-2D bar codes,and other optical codes), acoustic detection components (e.g.,microphones to identify tagged audio signals), or any suitablecombination thereof. In addition, a variety of information can bederived via the communication components 1364, such as location viaInternet Protocol (IP) geo-location, location via WI-FI® signaltriangulation, location via detecting a BLUETOOTH® or NFC beacon signalthat may indicate a particular location, and so forth.

In various example embodiments, one or more portions of the network 1380can be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the publicswitched telephone network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a WI-FI®network, another type of network, or a combination of two or more suchnetworks. For example, the network 1380 or a portion of the network 1380may include a wireless or cellular network, and the coupling 1382 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or another type of cellular orwireless coupling. In this example, the coupling 1382 can implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1xRTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard-setting organizations, other long rangeprotocols, or other data transfer technology.

In example embodiments, the instructions 1316 are transmitted orreceived over the network 1380 using a transmission medium via a networkinterface device (e.g., a network interface component included in thecommunication components 1364) and utilizing any one of a number ofwell-known transfer protocols (e.g., Hypertext Transfer Protocol(HTTP)). Similarly, in other example embodiments, the instructions 1316are transmitted or received using a transmission medium via the coupling1372 (e.g., a peer-to-peer coupling) to the devices 1370. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying the instructions 1316for execution by the machine 1300, and includes digital or analogcommunications signals or other intangible media to facilitatecommunication of such software.

Furthermore, the machine-readable medium 1338 is non-transitory (inother words, not having any transitory signals) in that it does notembody a propagating signal. However, labeling the machine-readablemedium 1338 “non-transitory” should not be construed to mean that themedium is incapable of movement; the medium 1338 should be considered asbeing transportable from one physical location to another. Additionally,since the machine-readable medium 1338 is tangible, the medium 1338 maybe considered to be a machine-readable device.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A method comprising: receiving, by a computingsystem, from a computing device capturing a video, context dataassociated with the computing device, the context data comprising aportion of an audio stream; analyzing the portion of the audio stream ofthe context data to determine that a media overlay of a plurality ofmedia overlays is relevant to at least one aspect of the context data;determining, by the computing system, that the media overlay comprises asmart widget selection corresponding to a display element comprisingdynamic content to be displayed on the media overlay based on thecontext data received from the computing device; based on determiningthat the media overlay comprises the smart widget selection, generating,by the computing system, content comprising information about the audiostream, the content to be displayed as the display element correspondingto the smart widget selection based on the portion of the audio streamfor the context data received from the computing device; andtransmitting, by the computing system to the computing device, the mediaoverlay and the generated content to be displayed as the display elementin the media overlay.
 2. The method of claim 1, further comprising:receiving, from the computing device, a message comprising the video andthe media overlay; and sending the message to a second computing device,wherein the message is displayed on the second computing device with themedia overlay applied to the video.
 3. The method of claim 1, whereinbefore analyzing the portion of the audio stream of the context data todetermine that the media overlay is relevant to at least one aspect ofthe context data, the method comprises analyzing the context data todetermine whether data in the context data triggers the media overlay,out of the plurality of media overlays, to be provided to the computingdevice.
 4. The method of claim 1, wherein the media overlay is a firstmedia overlay, and further comprising: determining that the context datafurther comprises geolocation data; and comparing the geolocation dataof the context data to a geolocation trigger for one or more of theplurality of media overlays to determine a match between the geolocationdata of the context data and a geolocation trigger for a second mediaoverlay; determining that the second media overlay comprises a secondsmart widget selection corresponding to a display element comprisingdynamic content to be displayed on the media overlay based on thecontext data comprising the geolocation data; generating contentcomprising information about a location corresponding to the geolocationdata, the content to be displayed as the display element correspondingthe second smart widget selection based on the geolocation data for thecontext data received from the computing device; transmitting the secondmedia overlay and the generated content to the computing device; andwherein the computing device renders the generated content comprisinginformation about the location in the display element on the secondmedia overlay based on attributes of the second smart widget selectionand causes the second media overlay to be displayed.
 5. The method ofclaim 1, wherein the media overlay is a first media overlay, and furthercomprising: determining that the context data further comprisesgeolocation data; determining that the geolocation data is associatedwith an event; and comparing the event to an event trigger for one ormore media overlays to determine a match between the event associatedwith the geolocation data of the context data and an event trigger for asecond media overlay; determining that the second media overlaycomprises a second smart widget selection corresponding to a displayelement comprising dynamic content to be displayed on the media overlaybased on the context data comprising the geolocation data; generatingcontent comprising information about the event corresponding to thegeolocation data, the content to be displayed as the display elementcorresponding the second smart widget selection based on the geolocationdata for the context data received from the computing device;transmitting the second media overlay and the generated content to thecomputing device; and wherein the computing device renders the generatedcontent comprising information about the event in the display element onthe second media overlay based on attributes of the second smart widgetselection and causes the second media overlay to be displayed.
 6. Themethod of claim 1, wherein the media overlay is a first media overlay,and further comprising: determining that the context data furthercomprises a date for the video to be included in a message; comparingthe date for the video to a date trigger for one or more media overlaysto determine a match between the date for the video and a date triggerfor a second media overlay; determining that the second media overlaycomprises a second smart widget selection corresponding to a displayelement comprising dynamic content to be displayed on the media overlaybased on the context data comprising the date for the video to beincluded in the message; generating content comprising information aboutthe date for the video, the content to be displayed as the displayelement corresponding the second smart widget selection based on thecontext data received from the computing device; transmitting the secondmedia overlay and the generated content to the computing device; andwherein the computing device renders the generated content comprisinginformation about the date for the video in the display element on thesecond media overlay based on attributes of the second smart widgetselection and causes the second media overlay to be displayed.
 7. Themethod of claim 1, wherein the context data further comprises contextdata associated with the video.
 8. A server computer comprising: one ormore hardware processors; and a computer-readable medium coupled withthe one or more hardware processors, the computer-readable mediumcomprising instructions stored thereon that are executable by the one ormore hardware processors to cause the server computer to performoperations comprising: receiving, from a computing device capturing avideo, context data associated with the computing device, the contextdata comprising a portion of an audio stream; analyzing the portion ofthe audio stream of the context data to determine that a media overlayof a plurality of media overlays is relevant to at least one aspect ofthe context data; determining that the media overlay comprises a smartwidget selection corresponding to a display element comprising dynamiccontent to be displayed on the media overlay based on the context datareceived from the computing device; based on determining that the mediaoverlay comprises the smart widget selection, generating contentcomprising information about the audio stream, the content to bedisplayed as the display element corresponding to the smart widgetselection based on the portion of the audio stream for the context datareceived from the computing device; and transmitting, to the computingdevice, the media overlay and the generated content to be displayed asthe display element in the media overlay.
 9. The server computer ofclaim 8, the operations further comprising: receiving, from thecomputing device, a message comprising the video and the media overlay;and sending the message to a second computing device, wherein themessage is displayed on the second computing device with the mediaoverlay applied to the video.
 10. The server computer of claim 8,wherein before analyzing the portion of the audio stream of the contextdata to determine that the media overlay is relevant to at least oneaspect of the context data, the method comprises analyzing the contextdata to determine whether data in the context data triggers the mediaoverlay, out of the plurality of media overlays, to be provided to thecomputing device.
 11. The server computer of claim 8, wherein the mediaoverlay is a first media overlay, and the operations further comprise:determining that the context data further comprises geolocation data;and comparing the geolocation data of the context data to a geolocationtrigger for one or more of the plurality of media overlays to determinea match between the geolocation data of the context data and ageolocation trigger for a second media overlay; determining that thesecond media overlay comprises a second smart widget selectioncorresponding to a display element comprising dynamic content to bedisplayed on the media overlay based on the context data comprising thegeolocation data; generating content comprising information about alocation corresponding to the geolocation data, the content to bedisplayed as the display element corresponding the second smart widgetselection based on the geolocation data for the context data receivedfrom the computing device; transmitting the second media overlay and thegenerated content to the computing device; and wherein the computingdevice renders the generated content comprising information about thelocation in the display element on the second media overlay based onattributes of the second smart widget selection and causes the secondmedia overlay to be displayed.
 12. The server computer of claim 8,wherein the media overlay is a first media overlay, and the operationsfurther comprising: determining that the context data further comprisesgeolocation data; determining that the geolocation data is associatedwith an event; and comparing the event to an event trigger for one ormore media overlays to determine a match between the event associatedwith the geolocation data of the context data and an event trigger for asecond media overlay; determining that the second media overlaycomprises a second smart widget selection corresponding to a displayelement comprising dynamic content to be displayed on the media overlaybased on the context data comprising the geolocation data; generatingcontent comprising information about the event corresponding to thegeolocation data, the content to be displayed as the display elementcorresponding the second smart widget selection based on the geolocationdata for the context data received from the computing device;transmitting the second media overlay and the generated content to thecomputing device; and wherein the computing device renders the generatedcontent comprising information about the event in the display element onthe second media overlay based on attributes of the second smart widgetselection and causes the second media overlay to be displayed.
 13. Theserver computer of claim 8, wherein the media overlay is a first mediaoverlay, and the operations further comprising: determining that thecontext data further comprises a date for the video to be included in amessage; comparing the date for the video to a date trigger for one ormore media overlays to determine a match between the date for the videoand a date trigger for a second media overlay; determining that thesecond media overlay comprises a second smart widget selectioncorresponding to a display element comprising dynamic content to bedisplayed on the media overlay based on the context data comprising thedate for the video to be included in the message; generating contentcomprising information about the date for the video, the content to bedisplayed as the display element corresponding the second smart widgetselection based on the context data received from the computing device;transmitting the second media overlay and the generated content to thecomputing device; and wherein the computing device renders the generatedcontent comprising information about the date for the video in thedisplay element on the second media overlay based on attributes of thesecond smart widget selection and causes the second media overlay to bedisplayed.
 14. The server computer of claim 8, wherein the context datafurther comprises context data associated with the video.
 15. Anon-transitory computer-readable medium comprising instructions storedthereon that are executable by at least one processor to cause acomputing device to perform operations comprising: receiving, from acomputing device capturing a video, context data associated with thecomputing device, the context data comprising a portion of an audiostream; analyzing the portion of the audio stream of the context data todetermine that a media overlay of a plurality of media overlays isrelevant to at least one aspect of the context data; determining thatthe media overlay comprises a smart widget selection corresponding to adisplay element comprising dynamic content to be displayed on the mediaoverlay based on the context data received from the computing device;based on determining that the media overlay comprises the smart widgetselection, generating content comprising information about the audiostream, the content to be displayed as the display element correspondingto the smart widget selection based on the portion of the audio streamfor the context data received from the computing device; andtransmitting, to the computing device, the media overlay and thegenerated content to be displayed as the display element in the mediaoverlay.
 16. The non-transitory computer-readable medium computer ofclaim 15, the operations further comprising: receiving, from thecomputing device, a message comprising the video and the media overlay;and sending the message to a second computing device, wherein themessage is displayed on the second computing device with the mediaoverlay applied to the video.
 17. The non-transitory computer-readablemedium computer of claim 15, wherein before analyzing the portion of theaudio stream of the context data to determine that the media overlay isrelevant to at least one aspect of the context data, the methodcomprises analyzing the context data to determine whether data in thecontext data triggers the media overlay, out of the plurality of mediaoverlays, to be provided to the computing device.
 18. The non-transitorycomputer-readable medium computer of claim 15, wherein the media overlayis a first media overlay, and the operations further comprise:determining that the context data further comprises geolocation data;and comparing the geolocation data of the context data to a geolocationtrigger for one or more of the plurality of media overlays to determinea match between the geolocation data of the context data and ageolocation trigger for a second media overlay; determining that thesecond media overlay comprises a second smart widget selectioncorresponding to a display element comprising dynamic content to bedisplayed on the media overlay based on the context data comprising thegeolocation data; generating content comprising information about alocation corresponding to the geolocation data, the content to bedisplayed as the display element corresponding the second smart widgetselection based on the geolocation data for the context data receivedfrom the computing device; transmitting the second media overlay and thegenerated content to the computing device; and wherein the computingdevice renders the generated content comprising information about thelocation in the display element on the second media overlay based onattributes of the second smart widget selection and causes the secondmedia overlay to be displayed.
 19. The non-transitory computer-readablemedium computer of claim 15, wherein the media overlay is a first mediaoverlay, and the operations further comprising: determining that thecontext data further comprises geolocation data; determining that thegeolocation data is associated with an event; and comparing the event toan event trigger for one or more media overlays to determine a matchbetween the event associated with the geolocation data of the contextdata and an event trigger for a second media overlay; determining thatthe second media overlay comprises a second smart widget selectioncorresponding to a display element comprising dynamic content to bedisplayed on the media overlay based on the context data comprising thegeolocation data; generating content comprising information about theevent corresponding to the geolocation data, the content to be displayedas the display element corresponding the second smart widget selectionbased on the geolocation data for the context data received from thecomputing device; transmitting the second media overlay and thegenerated content to the computing device; and wherein the computingdevice renders the generated content comprising information about theevent in the display element on the second media overlay based onattributes of the second smart widget selection and causes the secondmedia overlay to be displayed.
 20. The non-transitory computer-readablemedium computer of claim 15, wherein the media overlay is a first mediaoverlay, and the operations further comprising: determining that thecontext data further comprises a date for the video to be included in amessage; comparing the date for the video to a date trigger for one ormore media overlays to determine a match between the date for the videoand a date trigger for a second media overlay; determining that thesecond media overlay comprises a second smart widget selectioncorresponding to a display element comprising dynamic content to bedisplayed on the media overlay based on the context data comprising thedate for the video to be included in the message; generating contentcomprising information about the date for the video, the content to bedisplayed as the display element corresponding the second smart widgetselection based on the context data received from the computing device;transmitting the second media overlay and the generated content to thecomputing device; and wherein the computing device renders the generatedcontent comprising information about the date for the video in thedisplay element on the second media overlay based on attributes of thesecond smart widget selection and causes the second media overlay to bedisplayed.